Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a63a517378f15438b1fba5adee693e5de3a1c4d17ddfa7b160a68616f7afd9e

Tx prefix hash: efe7e53267a63f8f8f132c194e3c98c805e20664e48f28e37c4e76894295dbf8
Tx public key: d54086fcf3bfead85d2ba83caae840d4ada09330ef575a918265890b2b2a31df
Timestamp: 1706545509 Timestamp [UCT]: 2024-01-29 16:25:09 Age [y:d:h:m:s]: 01:140:14:38:31
Block: 945990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361505 RingCT/type: yes/0
Extra: 01d54086fcf3bfead85d2ba83caae840d4ada09330ef575a918265890b2b2a31df0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87007ceaf74108b8463252b50522e4a806ee3aaaee89402f6fb7718fbe9c98e9 0.600000000000 1404320 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": 946000, "vin": [ { "gen": { "height": 945990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87007ceaf74108b8463252b50522e4a806ee3aaaee89402f6fb7718fbe9c98e9" } } ], "extra": [ 1, 213, 64, 134, 252, 243, 191, 234, 216, 93, 43, 168, 60, 170, 232, 64, 212, 173, 160, 147, 48, 239, 87, 90, 145, 130, 101, 137, 11, 43, 42, 49, 223, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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