Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3059ac84fef57d093d744ed1b51e8e6a970306d4f14fa728c5c51903885056bc

Tx prefix hash: e53324854fc2642e593d11d1e114a2f05f48a58a7da734d784b8660a075e8eb7
Tx public key: 6ea353f26523bf845b54e0b4cf67e9ace86ad4f86d92fd9869bf7af76d7b96be
Timestamp: 1676209657 Timestamp [UCT]: 2023-02-12 13:47:37 Age [y:d:h:m:s]: 01:337:17:09:55
Block: 695401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502314 RingCT/type: yes/0
Extra: 016ea353f26523bf845b54e0b4cf67e9ace86ad4f86d92fd9869bf7af76d7b96be0211000000045029cbac000000000000000000

1 output(s) for total of 3.046826557000 dcy

stealth address amount amount idx
00: 3c82fa0773a40724300bfc50b31a0b2d7346b459f12a4b46e50f60414f601a4b 3.046826557000 1138356 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": 695411, "vin": [ { "gen": { "height": 695401 } } ], "vout": [ { "amount": 3046826557, "target": { "key": "3c82fa0773a40724300bfc50b31a0b2d7346b459f12a4b46e50f60414f601a4b" } } ], "extra": [ 1, 110, 163, 83, 242, 101, 35, 191, 132, 91, 84, 224, 180, 207, 103, 233, 172, 232, 106, 212, 248, 109, 146, 253, 152, 105, 191, 122, 247, 109, 123, 150, 190, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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