Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09c72942124bf73e7ff1a25fc1346634de568bc383c9c0cfaaa9867e6102d297

Tx prefix hash: 37d8d3a0bd57fb1e9ec8a9f8649983df888327882cf820d480564f1b1a5b6835
Tx public key: 60994a5ee99f83f7cab8bc27bd892895a5d88eb985a6148ae6f2a1d3e3bdef71
Timestamp: 1724973866 Timestamp [UCT]: 2024-08-29 23:24:26 Age [y:d:h:m:s]: 00:230:14:24:24
Block: 1098785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164668 RingCT/type: yes/0
Extra: 0160994a5ee99f83f7cab8bc27bd892895a5d88eb985a6148ae6f2a1d3e3bdef71021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 574c39f79560667bf9e45565420b06e9c0d6b3312312863d8f70bf6fa417c1f0 0.600000000000 1574620 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": 1098795, "vin": [ { "gen": { "height": 1098785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "574c39f79560667bf9e45565420b06e9c0d6b3312312863d8f70bf6fa417c1f0" } } ], "extra": [ 1, 96, 153, 74, 94, 233, 159, 131, 247, 202, 184, 188, 39, 189, 137, 40, 149, 165, 216, 142, 185, 133, 166, 20, 138, 230, 242, 161, 211, 227, 189, 239, 113, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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