Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 714f6ee18b0a8d1de50a11a3ada23eab974e4a2a4491a74734f13a77a74bde6e

Tx prefix hash: 3ca11695eefc808021d1b777694b6b44f78f0a9902695ddae1bf3fe4b9c479c4
Tx public key: 01f3961a30a5656dd403cceec1fd66d790bfe5bf14f9ef540d2666844bb70ae1
Timestamp: 1710516359 Timestamp [UCT]: 2024-03-15 15:25:59 Age [y:d:h:m:s]: 01:050:21:46:15
Block: 978947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297372 RingCT/type: yes/0
Extra: 0101f3961a30a5656dd403cceec1fd66d790bfe5bf14f9ef540d2666844bb70ae102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9abcaf6149c38a15632c84e68e9f4a149a575fb49eda48bb9364d7c17cda059 0.600000000000 1438976 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": 978957, "vin": [ { "gen": { "height": 978947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9abcaf6149c38a15632c84e68e9f4a149a575fb49eda48bb9364d7c17cda059" } } ], "extra": [ 1, 1, 243, 150, 26, 48, 165, 101, 109, 212, 3, 204, 238, 193, 253, 102, 215, 144, 191, 229, 191, 20, 249, 239, 84, 13, 38, 102, 132, 75, 183, 10, 225, 2, 17, 0, 0, 0, 4, 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