Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aaa06d2441050bce55213b3a58346a17e67ac9f06c671abaf2b64b89202def3

Tx prefix hash: 6343f8856c268352ce373904c3fb399c0b3eaf815b4120d14d80542cc674ba0e
Tx public key: 10810a3d440200e1102953118510972ef5661b7c09a2f23d6f2f11de798511ee
Timestamp: 1700768823 Timestamp [UCT]: 2023-11-23 19:47:03 Age [y:d:h:m:s]: 01:180:06:27:53
Block: 898120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390054 RingCT/type: yes/0
Extra: 0110810a3d440200e1102953118510972ef5661b7c09a2f23d6f2f11de798511ee02110000001775e3f0e9000000000000000000

1 output(s) for total of 0.648866868000 dcy

stealth address amount amount idx
00: 0195796295ccce284a36cff9959718d8a59a6abfd7d75e6bb24b5b7f0d456962 0.648866868000 1354525 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": 898130, "vin": [ { "gen": { "height": 898120 } } ], "vout": [ { "amount": 648866868, "target": { "key": "0195796295ccce284a36cff9959718d8a59a6abfd7d75e6bb24b5b7f0d456962" } } ], "extra": [ 1, 16, 129, 10, 61, 68, 2, 0, 225, 16, 41, 83, 17, 133, 16, 151, 46, 245, 102, 27, 124, 9, 162, 242, 61, 111, 47, 17, 222, 121, 133, 17, 238, 2, 17, 0, 0, 0, 23, 117, 227, 240, 233, 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