Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 904ca04bf9799e11dcfd1d394ca0a78327e6e4755b4594b6291da7560597663d

Tx prefix hash: 19d1738a4ef265d96014eac4d75e0f5644e75b69b308a19d627dd6649d7a948e
Tx public key: d2ade7467db8df220a9bb121551d98f68e341fb0507f72bb0cf6048f0dd2aa6b
Timestamp: 1699144891 Timestamp [UCT]: 2023-11-05 00:41:31 Age [y:d:h:m:s]: 01:178:06:23:20
Block: 884908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388356 RingCT/type: yes/0
Extra: 01d2ade7467db8df220a9bb121551d98f68e341fb0507f72bb0cf6048f0dd2aa6b02110000000533af99f4000000000000000000

1 output(s) for total of 0.717682669000 dcy

stealth address amount amount idx
00: 2049c253752e30ce21c6cb71062e78b781a6b9483bc735160de75bdc1bee59af 0.717682669000 1340657 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": 884918, "vin": [ { "gen": { "height": 884908 } } ], "vout": [ { "amount": 717682669, "target": { "key": "2049c253752e30ce21c6cb71062e78b781a6b9483bc735160de75bdc1bee59af" } } ], "extra": [ 1, 210, 173, 231, 70, 125, 184, 223, 34, 10, 155, 177, 33, 85, 29, 152, 246, 142, 52, 31, 176, 80, 127, 114, 187, 12, 246, 4, 143, 13, 210, 170, 107, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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