Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb32f6ade50ad64726dbf7853d8db84014b76376b01a8d1489fdd603d06b89be

Tx prefix hash: 603e2a7912487112db928dfbe1a30d2caa5c73abf7db724dd17cce34236a16b6
Tx public key: 51a9fa2597b21d9d555a23044dc24c2927d20bb43f5b95a0bbb667eefa935565
Timestamp: 1701001710 Timestamp [UCT]: 2023-11-26 12:28:30 Age [y:d:h:m:s]: 01:090:01:42:27
Block: 900045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325500 RingCT/type: yes/0
Extra: 0151a9fa2597b21d9d555a23044dc24c2927d20bb43f5b95a0bbb667eefa93556502110000001375e3f0e9000000000000000000

1 output(s) for total of 0.639406831000 dcy

stealth address amount amount idx
00: 00699bc73e3da7f8bb8d47ce23b748e24edf27d22f16cde53a52a10d797c6639 0.639406831000 1356522 of 0

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": 900055, "vin": [ { "gen": { "height": 900045 } } ], "vout": [ { "amount": 639406831, "target": { "key": "00699bc73e3da7f8bb8d47ce23b748e24edf27d22f16cde53a52a10d797c6639" } } ], "extra": [ 1, 81, 169, 250, 37, 151, 178, 29, 157, 85, 90, 35, 4, 77, 194, 76, 41, 39, 210, 11, 180, 63, 91, 149, 160, 187, 182, 103, 238, 250, 147, 85, 101, 2, 17, 0, 0, 0, 19, 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