Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a66c009e65c0fa1ddb5f86d21fd8f6c96fe5097c26c01e1d101c3d7c904d561c

Tx prefix hash: cef95976c23cda5df54ef19096f49d725a948938a646e7ff8a5c7ebf6190320d
Tx public key: a56c8423426a497f8b367475cf06ea6b3ad231f8686a610df7f9ae48a82ec75c
Timestamp: 1724338176 Timestamp [UCT]: 2024-08-22 14:49:36 Age [y:d:h:m:s]: 00:301:11:31:56
Block: 1093534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215227 RingCT/type: yes/0
Extra: 01a56c8423426a497f8b367475cf06ea6b3ad231f8686a610df7f9ae48a82ec75c02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1a19690abf352792d42c7416c5e1a71d9ffaaa7144ab0c9dd193f6cf44733f3 0.600000000000 1568497 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": 1093544, "vin": [ { "gen": { "height": 1093534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1a19690abf352792d42c7416c5e1a71d9ffaaa7144ab0c9dd193f6cf44733f3" } } ], "extra": [ 1, 165, 108, 132, 35, 66, 106, 73, 127, 139, 54, 116, 117, 207, 6, 234, 107, 58, 210, 49, 248, 104, 106, 97, 13, 247, 249, 174, 72, 168, 46, 199, 92, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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