Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a77b6d9bbe9e7644c90d5580f48de587383de097f77e3ce6cd8bebcb50bc60

Tx prefix hash: 0b710ce3c168f5e0394a6279fe2bdce95ad878d2cf230b00d93f6baa3ff68254
Tx public key: cbd49c4bc53e1d418ec1350358db51c41e81d1d3ce4ceca44d2730460f9b858c
Timestamp: 1706696368 Timestamp [UCT]: 2024-01-31 10:19:28 Age [y:d:h:m:s]: 01:067:00:30:02
Block: 947244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308969 RingCT/type: yes/0
Extra: 01cbd49c4bc53e1d418ec1350358db51c41e81d1d3ce4ceca44d2730460f9b858c02110000001d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc76344f98bbf3a2490878b6330b65f0ebc7064ff7bff212b02463a8b3a6ea0b 0.600000000000 1405592 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": 947254, "vin": [ { "gen": { "height": 947244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc76344f98bbf3a2490878b6330b65f0ebc7064ff7bff212b02463a8b3a6ea0b" } } ], "extra": [ 1, 203, 212, 156, 75, 197, 62, 29, 65, 142, 193, 53, 3, 88, 219, 81, 196, 30, 129, 209, 211, 206, 76, 236, 164, 77, 39, 48, 70, 15, 155, 133, 140, 2, 17, 0, 0, 0, 29, 89, 218, 211, 245, 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