Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa1ea81a9b14674dc53623f98f2fe0538b5098863c31939cf3410687d1df3e78

Tx prefix hash: 0cfecade50617939082767c73444ebbe293d87886ff7da52bc6795625dca5e7f
Tx public key: 5f2ea03e181d533f57a7dfd0f261d201c16a17468aca6131e388f40e59d508a2
Timestamp: 1711930193 Timestamp [UCT]: 2024-04-01 00:09:53 Age [y:d:h:m:s]: 01:034:03:09:10
Block: 990669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285349 RingCT/type: yes/0
Extra: 015f2ea03e181d533f57a7dfd0f261d201c16a17468aca6131e388f40e59d508a20211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e0928698e621d2a4d28113ac47e124b4c9d2d60db7dba09970ab35dfe0e5d4e 0.600000000000 1450993 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": 990679, "vin": [ { "gen": { "height": 990669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e0928698e621d2a4d28113ac47e124b4c9d2d60db7dba09970ab35dfe0e5d4e" } } ], "extra": [ 1, 95, 46, 160, 62, 24, 29, 83, 63, 87, 167, 223, 208, 242, 97, 210, 1, 193, 106, 23, 70, 138, 202, 97, 49, 227, 136, 244, 14, 89, 213, 8, 162, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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