Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b54fc75415edcbfc7b23f6ef8d2ff9c466c62552a518ac9361c13f84ca6c44d

Tx prefix hash: 45f0f67385aa7896d9f8efea3edfe419315786cd9714086ea6cf31c00e738294
Tx public key: 2dd553135f133b5916c19f3d3c22bcd2f2801b6bb1a2c3e11a6f13b862afb492
Timestamp: 1712489275 Timestamp [UCT]: 2024-04-07 11:27:55 Age [y:d:h:m:s]: 01:066:22:56:36
Block: 995265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308817 RingCT/type: yes/0
Extra: 012dd553135f133b5916c19f3d3c22bcd2f2801b6bb1a2c3e11a6f13b862afb4920211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cf430203987d7d90c6098a6d966e092e21e0e0e84627db451c06180f756cff3 0.600000000000 1455671 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": 995275, "vin": [ { "gen": { "height": 995265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cf430203987d7d90c6098a6d966e092e21e0e0e84627db451c06180f756cff3" } } ], "extra": [ 1, 45, 213, 83, 19, 95, 19, 59, 89, 22, 193, 159, 61, 60, 34, 188, 210, 242, 128, 27, 107, 177, 162, 195, 225, 26, 111, 19, 184, 98, 175, 180, 146, 2, 17, 0, 0, 0, 3, 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