Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5efcb2a3f0dad6675e910e4ec15abf173ff920957cab352076d9cf5df250ee6d

Tx prefix hash: 3dbb7704e283d4cbb6d8a05ac910f8df20358583c164393afaf2c4ca5f911973
Tx public key: 85cfac6297e12977e3a7d0b969211825ede25cd20bdc2a30b5f76e50f11ae617
Timestamp: 1708540446 Timestamp [UCT]: 2024-02-21 18:34:06 Age [y:d:h:m:s]: 01:073:13:53:13
Block: 962544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313633 RingCT/type: yes/0
Extra: 0185cfac6297e12977e3a7d0b969211825ede25cd20bdc2a30b5f76e50f11ae6170211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c4403f0b6bd4d13cc8c148409f60c0238a4d0e267c94a93faa90188b6dc9589 0.600000000000 1422185 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": 962554, "vin": [ { "gen": { "height": 962544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c4403f0b6bd4d13cc8c148409f60c0238a4d0e267c94a93faa90188b6dc9589" } } ], "extra": [ 1, 133, 207, 172, 98, 151, 225, 41, 119, 227, 167, 208, 185, 105, 33, 24, 37, 237, 226, 92, 210, 11, 220, 42, 48, 181, 247, 110, 80, 241, 26, 230, 23, 2, 17, 0, 0, 0, 3, 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