Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b84c87303de0f261274e578a8aa4eb0cecef14ce812087519480b932a4d49a59

Tx prefix hash: 28754d93aebb332f8cc561b08a6f365863cb6a9040fa7744d98b752cbe83373a
Tx public key: 5c1f219988f918d0c8fc950df3bb52b66d3d5cdd17a8a8adb208db2768f924fe
Timestamp: 1757526029 Timestamp [UCT]: 2025-09-10 17:40:29 Age [y:d:h:m:s]: 00:076:18:52:17
Block: 1365565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54972 RingCT/type: yes/0
Extra: 015c1f219988f918d0c8fc950df3bb52b66d3d5cdd17a8a8adb208db2768f924fe021100000008ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2247792eeed12286c0bbee04cb2d8b1c3a3383c21e8573f3ecf47e5b6e76cb2d 0.600000000000 1853604 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": 1365575, "vin": [ { "gen": { "height": 1365565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2247792eeed12286c0bbee04cb2d8b1c3a3383c21e8573f3ecf47e5b6e76cb2d" } } ], "extra": [ 1, 92, 31, 33, 153, 136, 249, 24, 208, 200, 252, 149, 13, 243, 187, 82, 182, 109, 61, 92, 221, 23, 168, 168, 173, 178, 8, 219, 39, 104, 249, 36, 254, 2, 17, 0, 0, 0, 8, 173, 121, 72, 208, 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