Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b50f372aabe7ab97a5f3288bbb04a839f4fc5855dfb70b43d663498d251cd48

Tx prefix hash: bcf7cb606d272967c42547337189e473ece78159d7ed9e3d8c69ad1009356b11
Tx public key: 0a44efb96ffb2aa5800f25f5a59e8ddcd5791c88b71e365118bbf77a22faf946
Timestamp: 1763176416 Timestamp [UCT]: 2025-11-15 03:13:36 Age [y:d:h:m:s]: 00:013:03:08:54
Block: 1412386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9400 RingCT/type: yes/0
Extra: 010a44efb96ffb2aa5800f25f5a59e8ddcd5791c88b71e365118bbf77a22faf946021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5a656dad8f417a72fdfd9f5459edcee2e5bf25aefed8723936d362a9631df06 0.600000000000 1900853 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": 1412396, "vin": [ { "gen": { "height": 1412386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5a656dad8f417a72fdfd9f5459edcee2e5bf25aefed8723936d362a9631df06" } } ], "extra": [ 1, 10, 68, 239, 185, 111, 251, 42, 165, 128, 15, 37, 245, 165, 158, 141, 220, 213, 121, 28, 136, 183, 30, 54, 81, 24, 187, 247, 122, 34, 250, 249, 70, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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