Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee3e5cd1701d4b10b71256f286cab4540e2dbfb8c7b6e1cfcf39f5640721e992

Tx prefix hash: 0a790ce5e33c109b455870f084f762c7002d97d6fcf47da37c15d06e06573345
Tx public key: b4bc8ea8b01697a8ee0e64f3afcb04fb78024819e584b97e9b18a4abbf8874ad
Timestamp: 1760380055 Timestamp [UCT]: 2025-10-13 18:27:35 Age [y:d:h:m:s]: 00:026:01:22:32
Block: 1389215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18649 RingCT/type: yes/0
Extra: 01b4bc8ea8b01697a8ee0e64f3afcb04fb78024819e584b97e9b18a4abbf8874ad0211000000078368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc33139b6ad1b14147d56fef68ffb7ac3bc944463ca3d921a1c3b33b9a1027e6 0.600000000000 1877444 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": 1389225, "vin": [ { "gen": { "height": 1389215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc33139b6ad1b14147d56fef68ffb7ac3bc944463ca3d921a1c3b33b9a1027e6" } } ], "extra": [ 1, 180, 188, 142, 168, 176, 22, 151, 168, 238, 14, 100, 243, 175, 203, 4, 251, 120, 2, 72, 25, 229, 132, 185, 126, 155, 24, 164, 171, 191, 136, 116, 173, 2, 17, 0, 0, 0, 7, 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