Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 390f5db0cb7185630d35de613a9ba06f2d7cbed955c146684ea7c3dffb92ead5

Tx prefix hash: 93d06b1d3ae9422ef49c20ffdb20b85a56091127030323cdee939fe4a75687f8
Tx public key: 2da2af205ed3af230418d903921c0c3ebf55c86badd517d77431ae761ad8b45e
Timestamp: 1719674749 Timestamp [UCT]: 2024-06-29 15:25:49 Age [y:d:h:m:s]: 00:259:09:56:51
Block: 1054854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185369 RingCT/type: yes/0
Extra: 012da2af205ed3af230418d903921c0c3ebf55c86badd517d77431ae761ad8b45e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7add7c9c94e7c9aa6479f7e23adc345fa6b6da802104822d861f23daa9bb2cf1 0.600000000000 1525245 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": 1054864, "vin": [ { "gen": { "height": 1054854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7add7c9c94e7c9aa6479f7e23adc345fa6b6da802104822d861f23daa9bb2cf1" } } ], "extra": [ 1, 45, 162, 175, 32, 94, 211, 175, 35, 4, 24, 217, 3, 146, 28, 12, 62, 191, 85, 200, 107, 173, 213, 23, 215, 116, 49, 174, 118, 26, 216, 180, 94, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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