Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85fe6c27314ce91cffea93cf342dfde0bb026f78d154d7ed72a667fe0133c4c1

Tx prefix hash: cce65d66848a66812d306f4c8b4272850ce75605a8dcc61e9a3d1f93607c200b
Tx public key: 6b26a6aa8a2ac20ec375844d18847a50b905afe84212b2c51d33e29972aac1fc
Timestamp: 1749425443 Timestamp [UCT]: 2025-06-08 23:30:43 Age [y:d:h:m:s]: 00:153:22:34:32
Block: 1300963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107694 RingCT/type: yes/0
Extra: 016b26a6aa8a2ac20ec375844d18847a50b905afe84212b2c51d33e29972aac1fc021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7ab7848c142617a954814842b19f71e0ee20938ed2a3c8a75291d1773491282 0.600000000000 1788516 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": 1300973, "vin": [ { "gen": { "height": 1300963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7ab7848c142617a954814842b19f71e0ee20938ed2a3c8a75291d1773491282" } } ], "extra": [ 1, 107, 38, 166, 170, 138, 42, 194, 14, 195, 117, 132, 77, 24, 132, 122, 80, 185, 5, 175, 232, 66, 18, 178, 197, 29, 51, 226, 153, 114, 170, 193, 252, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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