Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 589fd0bf297a784c6383029a4ea8e879a364f82e010e9cd74f97025cb640b70d

Tx prefix hash: 079572b10e061eed6412ba931941c2818dfd43d5a79a4c5345bb8867738015c1
Tx public key: 3a9b40ccc90903e628c1bf801bbbbc06e71484f021818261b4dfa30beefaa906
Timestamp: 1705908991 Timestamp [UCT]: 2024-01-22 07:36:31 Age [y:d:h:m:s]: 01:035:00:12:16
Block: 940688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286099 RingCT/type: yes/0
Extra: 013a9b40ccc90903e628c1bf801bbbbc06e71484f021818261b4dfa30beefaa9060211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c42b496917ee012bcc5fb8aef92e36b53ac2abad7b6fd1f111dbf7492ac6c7b 0.600000000000 1398828 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": 940698, "vin": [ { "gen": { "height": 940688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c42b496917ee012bcc5fb8aef92e36b53ac2abad7b6fd1f111dbf7492ac6c7b" } } ], "extra": [ 1, 58, 155, 64, 204, 201, 9, 3, 230, 40, 193, 191, 128, 27, 187, 188, 6, 231, 20, 132, 240, 33, 129, 130, 97, 180, 223, 163, 11, 238, 250, 169, 6, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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