Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dd2c223fd5c9fc27f501e23cb509eeb8deada300a632ef01ecab4e61748d69a

Tx prefix hash: 39fc84b08dd7397647398297d7944bf0ec738336fa5c4d0f70067161408cbdf8
Tx public key: bf52c4a90cd96ce5c6d9e461d4a28a9336a802ceb0e35b894b4cbf0b4da108e1
Timestamp: 1703105102 Timestamp [UCT]: 2023-12-20 20:45:02 Age [y:d:h:m:s]: 01:337:20:17:38
Block: 917507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500290 RingCT/type: yes/0
Extra: 01bf52c4a90cd96ce5c6d9e461d4a28a9336a802ceb0e35b894b4cbf0b4da108e102110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82010219f5ad6d204d083b26673ef9376854880d680809e2f31313d29e59fda2 0.600000000000 1375089 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": 917517, "vin": [ { "gen": { "height": 917507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82010219f5ad6d204d083b26673ef9376854880d680809e2f31313d29e59fda2" } } ], "extra": [ 1, 191, 82, 196, 169, 12, 217, 108, 229, 198, 217, 228, 97, 212, 162, 138, 147, 54, 168, 2, 206, 176, 227, 91, 137, 75, 76, 191, 11, 77, 161, 8, 225, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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