Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79f96b7dd541c50dfbbf4187e8ec1ef46c5c678ca594593a706643fb46acee67

Tx prefix hash: 9916b5f02f72ad9bf13d80688e9d638bad1b14a01c1042c8255edee52bc9a1f9
Tx public key: 647b6a5f307d22e2dc109f383f557f4322a65c55b29617c91922aa963410ec8a
Timestamp: 1709451609 Timestamp [UCT]: 2024-03-03 07:40:09 Age [y:d:h:m:s]: 01:036:05:43:24
Block: 970111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286891 RingCT/type: yes/0
Extra: 01647b6a5f307d22e2dc109f383f557f4322a65c55b29617c91922aa963410ec8a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4986231dd734cab05a47d88e6e59f6e7050eaaf1480d8f836d2a2efdf30dba44 0.600000000000 1429960 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": 970121, "vin": [ { "gen": { "height": 970111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4986231dd734cab05a47d88e6e59f6e7050eaaf1480d8f836d2a2efdf30dba44" } } ], "extra": [ 1, 100, 123, 106, 95, 48, 125, 34, 226, 220, 16, 159, 56, 63, 85, 127, 67, 34, 166, 92, 85, 178, 150, 23, 201, 25, 34, 170, 150, 52, 16, 236, 138, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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