Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae712b303f1340cb07feb060a38e4a465c7aa7eba811c37a449487da68555bd4

Tx prefix hash: 346fcba19359bda6994076153befed716023138b691bfd39292f603f4c107f73
Tx public key: 15399ea9753d8633e9a2b4e7d2e167df518708b1f582f19791d9860ce1c5fdf0
Timestamp: 1751136344 Timestamp [UCT]: 2025-06-28 18:45:44 Age [y:d:h:m:s]: 00:143:19:22:49
Block: 1314691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100879 RingCT/type: yes/0
Extra: 0115399ea9753d8633e9a2b4e7d2e167df518708b1f582f19791d9860ce1c5fdf00211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13de3e351c3875beb060f08012e65b7a5ca7f615f3d792353d7b7875010e0c42 0.600000000000 1802342 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": 1314701, "vin": [ { "gen": { "height": 1314691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13de3e351c3875beb060f08012e65b7a5ca7f615f3d792353d7b7875010e0c42" } } ], "extra": [ 1, 21, 57, 158, 169, 117, 61, 134, 51, 233, 162, 180, 231, 210, 225, 103, 223, 81, 135, 8, 177, 245, 130, 241, 151, 145, 217, 134, 12, 225, 197, 253, 240, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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