Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 660f25d53022d59425febcc387444b8733c472efbce9c4cbcfc3d2cefade23e2

Tx prefix hash: f1a13ba241cee0a2b8729dffe6a34fdebc92ce98dad4a14adf16a578c56643a3
Tx public key: d068a6a94b16b80bd4f99dcaf3a4b7565afe2c81bbfd37f27696c7c0b21a1abe
Timestamp: 1702962227 Timestamp [UCT]: 2023-12-19 05:03:47 Age [y:d:h:m:s]: 01:118:23:20:50
Block: 916309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346154 RingCT/type: yes/0
Extra: 01d068a6a94b16b80bd4f99dcaf3a4b7565afe2c81bbfd37f27696c7c0b21a1abe02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1240ebe863cb8cf6eea612c1c95c78f5ddd74d9ea19c373fe5a6d5b31406f16 0.600000000000 1373795 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": 916319, "vin": [ { "gen": { "height": 916309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1240ebe863cb8cf6eea612c1c95c78f5ddd74d9ea19c373fe5a6d5b31406f16" } } ], "extra": [ 1, 208, 104, 166, 169, 75, 22, 184, 11, 212, 249, 157, 202, 243, 164, 183, 86, 90, 254, 44, 129, 187, 253, 55, 242, 118, 150, 199, 192, 178, 26, 26, 190, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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