Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539b6828d4bce9af42b7f8c84604165959140a2525d3bfe01cf6420d122a5202

Tx prefix hash: 4f3937274d8d4d4023d60a2377d26c30ec29a467b8d05175435f95b7928e7732
Tx public key: 9b120ddd22b0bf01b533b7012b6a0028ad3bbfcca46a0d1ad3cf65f7ce85ae50
Timestamp: 1705348168 Timestamp [UCT]: 2024-01-15 19:49:28 Age [y:d:h:m:s]: 01:154:02:39:40
Block: 936065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371172 RingCT/type: yes/0
Extra: 019b120ddd22b0bf01b533b7012b6a0028ad3bbfcca46a0d1ad3cf65f7ce85ae500211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ae8d281cfeb87832c393c66b436531c7f4e558af34da91c5f20e965e6a6853c 0.600000000000 1394087 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": 936075, "vin": [ { "gen": { "height": 936065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ae8d281cfeb87832c393c66b436531c7f4e558af34da91c5f20e965e6a6853c" } } ], "extra": [ 1, 155, 18, 13, 221, 34, 176, 191, 1, 181, 51, 183, 1, 43, 106, 0, 40, 173, 59, 191, 204, 164, 106, 13, 26, 211, 207, 101, 247, 206, 133, 174, 80, 2, 17, 0, 0, 0, 2, 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