Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc28de2455087e55ceafb23221c4d72a7a7746105f9a2c34959c364921440269

Tx prefix hash: fb07129f45a2b9eacfab7feb17268de3c7fd02a98b451c9b95dd71e76541a018
Tx public key: f67bce8a41c6becc836f6419312f3c7b23fac93477d3ddac0a0dc5ebe7713f6a
Timestamp: 1738142742 Timestamp [UCT]: 2025-01-29 09:25:42 Age [y:d:h:m:s]: 00:296:05:35:13
Block: 1207552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209468 RingCT/type: yes/0
Extra: 01f67bce8a41c6becc836f6419312f3c7b23fac93477d3ddac0a0dc5ebe7713f6a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fb452a3f99d93892da27b921cbedf9acde0376ea832632f9b04b5b2e12ea9cd 0.600000000000 1694277 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": 1207562, "vin": [ { "gen": { "height": 1207552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fb452a3f99d93892da27b921cbedf9acde0376ea832632f9b04b5b2e12ea9cd" } } ], "extra": [ 1, 246, 123, 206, 138, 65, 198, 190, 204, 131, 111, 100, 25, 49, 47, 60, 123, 35, 250, 201, 52, 119, 211, 221, 172, 10, 13, 197, 235, 231, 113, 63, 106, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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