Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d60d88475b7ba3de1f1fe522ce3e1166a75525560f7ff61b88b7b6f13906e8c

Tx prefix hash: b48bf87843ce781f73b259ab781bd768c7b8fa9572f046b8943c7eb76ae5f5ff
Tx public key: d9c39754e19e0d8f5986aff7b7afaada762f20e38fea7f64947fa03cc9eb30e2
Timestamp: 1708085297 Timestamp [UCT]: 2024-02-16 12:08:17 Age [y:d:h:m:s]: 01:008:22:28:46
Block: 958775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267389 RingCT/type: yes/0
Extra: 01d9c39754e19e0d8f5986aff7b7afaada762f20e38fea7f64947fa03cc9eb30e20211000000013f0590f7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc2b2ecb81b2f8f49b8cb9991eacfca80b4d55535bf2adb25669b2157b9896d6 0.600000000000 1418136 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": 958785, "vin": [ { "gen": { "height": 958775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc2b2ecb81b2f8f49b8cb9991eacfca80b4d55535bf2adb25669b2157b9896d6" } } ], "extra": [ 1, 217, 195, 151, 84, 225, 158, 13, 143, 89, 134, 175, 247, 183, 175, 170, 218, 118, 47, 32, 227, 143, 234, 127, 100, 148, 127, 160, 60, 201, 235, 48, 226, 2, 17, 0, 0, 0, 1, 63, 5, 144, 247, 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