Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 960647e178f6e90e01ee0445931f4b237c966b08a38fd166d5b78acab4d825b8

Tx prefix hash: af55563ae942aaa516593e96db4c48a1cf970e4c82632203e189e9fe28bf51e4
Tx public key: 3f43da0446eec9115ab3587d321ce2d69eef32512ed551a9d3f4e5bd0dc92eed
Timestamp: 1726352034 Timestamp [UCT]: 2024-09-14 22:13:54 Age [y:d:h:m:s]: 00:254:20:49:04
Block: 1110220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182011 RingCT/type: yes/0
Extra: 013f43da0446eec9115ab3587d321ce2d69eef32512ed551a9d3f4e5bd0dc92eed02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e31821e0a8005318ae90310cbcbf3e955e37cb3dc93b1627d1c6dc9b313e6d2 0.600000000000 1588745 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": 1110230, "vin": [ { "gen": { "height": 1110220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e31821e0a8005318ae90310cbcbf3e955e37cb3dc93b1627d1c6dc9b313e6d2" } } ], "extra": [ 1, 63, 67, 218, 4, 70, 238, 201, 17, 90, 179, 88, 125, 50, 28, 226, 214, 158, 239, 50, 81, 46, 213, 81, 169, 211, 244, 229, 189, 13, 201, 46, 237, 2, 17, 0, 0, 0, 2, 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