Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6f668a2181e0810f38d9ff492dca06b3327ebd006c5e97eaf5df695a88d816c

Tx prefix hash: aaa6e80f8a5773640a0fd94959a3a41184a3ea7b14da572c3b56afbc7b72e8d5
Tx public key: 0a47d0f0dc57c975563d6f2ec6bc2b9e625329a1f571e6ec83e97c617c73e4a5
Timestamp: 1722561754 Timestamp [UCT]: 2024-08-02 01:22:34 Age [y:d:h:m:s]: 00:314:12:27:50
Block: 1078790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224688 RingCT/type: yes/0
Extra: 010a47d0f0dc57c975563d6f2ec6bc2b9e625329a1f571e6ec83e97c617c73e4a5021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4acea19a62d000f6607bf83a72a7b6988791a3963f5398229f381910a84190a9 0.600000000000 1551473 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": 1078800, "vin": [ { "gen": { "height": 1078790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4acea19a62d000f6607bf83a72a7b6988791a3963f5398229f381910a84190a9" } } ], "extra": [ 1, 10, 71, 208, 240, 220, 87, 201, 117, 86, 61, 111, 46, 198, 188, 43, 158, 98, 83, 41, 161, 245, 113, 230, 236, 131, 233, 124, 97, 124, 115, 228, 165, 2, 17, 0, 0, 0, 1, 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