Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1afeaac79e6d305d8bb63189c15b684f95bd9fa33413ba2223444c52297260c5

Tx prefix hash: 9faa3f032e0d099e7ee8d890d24b2c29d64ed940dc4dcae3d47110fb59f6d97e
Tx public key: f304fd4d77a86bdd687240d5436c942ea5ea7916f55a23e57d8e9c99b41c52eb
Timestamp: 1702388321 Timestamp [UCT]: 2023-12-12 13:38:41 Age [y:d:h:m:s]: 01:023:22:05:27
Block: 911565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278437 RingCT/type: yes/0
Extra: 01f304fd4d77a86bdd687240d5436c942ea5ea7916f55a23e57d8e9c99b41c52eb021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f34dade3ee0812e45659e9ba23da9f22a0fe6cbaf2661db090f460868020026 0.600000000000 1368777 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": 911575, "vin": [ { "gen": { "height": 911565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f34dade3ee0812e45659e9ba23da9f22a0fe6cbaf2661db090f460868020026" } } ], "extra": [ 1, 243, 4, 253, 77, 119, 168, 107, 221, 104, 114, 64, 213, 67, 108, 148, 46, 165, 234, 121, 22, 245, 90, 35, 229, 125, 142, 156, 153, 180, 28, 82, 235, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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