Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa55f72467ab61c396c886d4c706574af7f15e051c3ee966ae393fdd5f404ae5

Tx prefix hash: a06444207f7261dece7e6cea7a094e1cb010eb82352e6d5980a1c0582ba8e064
Tx public key: edb36f296eca97f48d4b46afe69a848144a93af8b05a896b49cab3ee0d40c6bf
Timestamp: 1721103215 Timestamp [UCT]: 2024-07-16 04:13:35 Age [y:d:h:m:s]: 00:131:23:12:02
Block: 1066718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94415 RingCT/type: yes/0
Extra: 01edb36f296eca97f48d4b46afe69a848144a93af8b05a896b49cab3ee0d40c6bf02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d542073d9aab27acf7f6b6f79232d8a281dd37557856bc7ffb9701e4ab43073 0.600000000000 1537385 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": 1066728, "vin": [ { "gen": { "height": 1066718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d542073d9aab27acf7f6b6f79232d8a281dd37557856bc7ffb9701e4ab43073" } } ], "extra": [ 1, 237, 179, 111, 41, 110, 202, 151, 244, 141, 75, 70, 175, 230, 154, 132, 129, 68, 169, 58, 248, 176, 90, 137, 107, 73, 202, 179, 238, 13, 64, 198, 191, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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