Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 360f23735bf176863a90c88ef31a36094e53e8ef92d0c3d59c1a6e4fc306e8e3

Tx prefix hash: 2a4d86eaf7b56d32fca9953337a9b66d892a14553c639694ee98161377b446b2
Tx public key: e9a5ddc3c4fe8d41e53bb78871b7bdfe5ee8e1ce92701bc9ae6d69479e8757cc
Timestamp: 1678539951 Timestamp [UCT]: 2023-03-11 13:05:51 Age [y:d:h:m:s]: 02:040:09:21:46
Block: 714736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550418 RingCT/type: yes/0
Extra: 01e9a5ddc3c4fe8d41e53bb78871b7bdfe5ee8e1ce92701bc9ae6d69479e8757cc021100000003835e4d22000000000000000000

1 output(s) for total of 2.628953004000 dcy

stealth address amount amount idx
00: 6de0c742754acecbb31cffc367069547c06b26e61778cff946d6c5078e03def4 2.628953004000 1159003 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": 714746, "vin": [ { "gen": { "height": 714736 } } ], "vout": [ { "amount": 2628953004, "target": { "key": "6de0c742754acecbb31cffc367069547c06b26e61778cff946d6c5078e03def4" } } ], "extra": [ 1, 233, 165, 221, 195, 196, 254, 141, 65, 229, 59, 183, 136, 113, 183, 189, 254, 94, 232, 225, 206, 146, 112, 27, 201, 174, 109, 105, 71, 158, 135, 87, 204, 2, 17, 0, 0, 0, 3, 131, 94, 77, 34, 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