Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dacfae0b064b74c010f35eb5f7247e1ba5a9024ae07af64acf2f2afdbace75cd

Tx prefix hash: fe64c052401d3264630e3f4b0159364d9405e542d02b416b9c2d007f87a1fc57
Tx public key: af89765daaddc067fa52bae3b8d552f834583c1bc96ca1b7fd5d3857f7d2b9d4
Timestamp: 1720130259 Timestamp [UCT]: 2024-07-04 21:57:39 Age [y:d:h:m:s]: 00:111:00:37:20
Block: 1058630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79508 RingCT/type: yes/0
Extra: 01af89765daaddc067fa52bae3b8d552f834583c1bc96ca1b7fd5d3857f7d2b9d40211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbfc125685a31e2da7a35e352e8f929c7dd7250c4f10cacfac0b0b4a6e255266 0.600000000000 1529087 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": 1058640, "vin": [ { "gen": { "height": 1058630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbfc125685a31e2da7a35e352e8f929c7dd7250c4f10cacfac0b0b4a6e255266" } } ], "extra": [ 1, 175, 137, 118, 93, 170, 221, 192, 103, 250, 82, 186, 227, 184, 213, 82, 248, 52, 88, 60, 27, 201, 108, 161, 183, 253, 93, 56, 87, 247, 210, 185, 212, 2, 17, 0, 0, 0, 7, 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