Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df4e147057992e0b28e719cf212d3ccae3072fdd66d46adee7d9e366a792947f

Tx prefix hash: cf8fad10fec109838e5a268b763c6a3067ed6809a143e49d74ce4b73eefc6957
Tx public key: d0ecc1f4d723a13ad590cf8bc14a22ffa5580283309fcfd62fbcc591fa42ea4e
Timestamp: 1721044761 Timestamp [UCT]: 2024-07-15 11:59:21 Age [y:d:h:m:s]: 01:117:00:37:00
Block: 1066234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342134 RingCT/type: yes/0
Extra: 01d0ecc1f4d723a13ad590cf8bc14a22ffa5580283309fcfd62fbcc591fa42ea4e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61e7660b0f3553376e62023a357383ee8262d32fab3ce9cc310f5e89f8cd3e43 0.600000000000 1536807 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": 1066244, "vin": [ { "gen": { "height": 1066234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61e7660b0f3553376e62023a357383ee8262d32fab3ce9cc310f5e89f8cd3e43" } } ], "extra": [ 1, 208, 236, 193, 244, 215, 35, 161, 58, 213, 144, 207, 139, 193, 74, 34, 255, 165, 88, 2, 131, 48, 159, 207, 214, 47, 188, 197, 145, 250, 66, 234, 78, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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