Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10fd47fc4975e59a6c5635a0e0cf96e3113a64c065e021d4ffa313a6626f1812

Tx prefix hash: cf4cc50a145367eb69512d1df0ad0df303290987eb4724866bb9487b0f02c465
Tx public key: 7cf93061e576f5d5977699fdf8b7e0e8e4e6f1fab94aebeb54d77c5e7c5a3123
Timestamp: 1758975702 Timestamp [UCT]: 2025-09-27 12:21:42 Age [y:d:h:m:s]: 00:127:07:48:15
Block: 1377567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90994 RingCT/type: yes/0
Extra: 017cf93061e576f5d5977699fdf8b7e0e8e4e6f1fab94aebeb54d77c5e7c5a3123021100000006a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b653e2e76adc1aa5647b16c37ca98007f9b6020fb2b5b276f97d63ab52fd39d 0.600000000000 1865662 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": 1377577, "vin": [ { "gen": { "height": 1377567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b653e2e76adc1aa5647b16c37ca98007f9b6020fb2b5b276f97d63ab52fd39d" } } ], "extra": [ 1, 124, 249, 48, 97, 229, 118, 245, 213, 151, 118, 153, 253, 248, 183, 224, 232, 228, 230, 241, 250, 185, 74, 235, 235, 84, 215, 124, 94, 124, 90, 49, 35, 2, 17, 0, 0, 0, 6, 165, 220, 205, 121, 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