Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e3166f9f57ba6c27a9c17e70947eb9be6d96b61d872f7fcda7caf3a545044c5

Tx prefix hash: 398ff073dcf9a336c4d235262b9d77209ae81fb4e31d5b5ea5cbde787a6dc171
Tx public key: dd45cca46389054d6df32a154c6de7767c89724491afd6524c3f2e0d1142a05b
Timestamp: 1694440188 Timestamp [UCT]: 2023-09-11 13:49:48 Age [y:d:h:m:s]: 01:128:10:00:19
Block: 845840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353088 RingCT/type: yes/0
Extra: 01dd45cca46389054d6df32a154c6de7767c89724491afd6524c3f2e0d1142a05b02110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.966898792000 dcy

stealth address amount amount idx
00: 18d8973584069644dd1adf97227dc74b4f50a513d5f3a7827102c10b8e94923e 0.966898792000 1299262 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": 845850, "vin": [ { "gen": { "height": 845840 } } ], "vout": [ { "amount": 966898792, "target": { "key": "18d8973584069644dd1adf97227dc74b4f50a513d5f3a7827102c10b8e94923e" } } ], "extra": [ 1, 221, 69, 204, 164, 99, 137, 5, 77, 109, 243, 42, 21, 76, 109, 231, 118, 124, 137, 114, 68, 145, 175, 214, 82, 76, 63, 46, 13, 17, 66, 160, 91, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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