Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b502a90d76718b9950287181c98d90c27c0b652b6ced3fd239fc6ff3a93f60e

Tx prefix hash: 8d8ae0c097c12be79e0a745357e3276912379d29be79524ac9831eb712f9ac72
Tx public key: f1cabae9bf8e13b855d3d4dcadf79d86a8dfcf8d0e40baeead6cdfdb771808bd
Timestamp: 1757776638 Timestamp [UCT]: 2025-09-13 15:17:18 Age [y:d:h:m:s]: 00:114:08:38:45
Block: 1367625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81914 RingCT/type: yes/0
Extra: 01f1cabae9bf8e13b855d3d4dcadf79d86a8dfcf8d0e40baeead6cdfdb771808bd021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4c1c3678a45930ea2fe004746adb6a176646ccab4245a68d52881a8cc72320d 0.600000000000 1855664 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": 1367635, "vin": [ { "gen": { "height": 1367625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4c1c3678a45930ea2fe004746adb6a176646ccab4245a68d52881a8cc72320d" } } ], "extra": [ 1, 241, 202, 186, 233, 191, 142, 19, 184, 85, 211, 212, 220, 173, 247, 157, 134, 168, 223, 207, 141, 14, 64, 186, 238, 173, 108, 223, 219, 119, 24, 8, 189, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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