Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: dddf0be60fe470031a9b14064f9000e5b602120768a439e6b6757c10ac8517ee

Tx prefix hash: ced6c5478804e45618aec187991b44e3fa0f99b952bc49a9b6c2a38dd29ce8e5
Tx public key: 4286b7f32b4f7cbd7c71132c0e7a64c4234472501c57d764df4a64d6576f19c2
Timestamp: 1749557658 Timestamp [UCT]: 2025-06-10 12:14:18 Age [y:d:h:m:s]: 00:156:17:53:12
Block: 1302064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109691 RingCT/type: yes/0
Extra: 014286b7f32b4f7cbd7c71132c0e7a64c4234472501c57d764df4a64d6576f19c202110000001043846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb5ea58af4eded664d44c0a81737ea7d3cee3e66256d942fba5a3f6674185f63 0.600000000000 1789633 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1302074, "vin": [ { "gen": { "height": 1302064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb5ea58af4eded664d44c0a81737ea7d3cee3e66256d942fba5a3f6674185f63" } } ], "extra": [ 1, 66, 134, 183, 243, 43, 79, 124, 189, 124, 113, 19, 44, 14, 122, 100, 196, 35, 68, 114, 80, 28, 87, 215, 100, 223, 74, 100, 214, 87, 111, 25, 194, 2, 17, 0, 0, 0, 16, 67, 132, 109, 102, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8