Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf21c96dbec9cbbff1863f7000111a04e9e58d0117e0c539fefe8e61166d9823

Tx prefix hash: 96e02785f35e35a89d55f6b604530931ca3b224d579e9dfcef60bbc81ac50b80
Tx public key: 7f1cb5dacd2618d1338e9d53d4b1bc3bda96b5e0fc086b53f7315816784bdf26
Timestamp: 1720052437 Timestamp [UCT]: 2024-07-04 00:20:37 Age [y:d:h:m:s]: 00:260:23:28:04
Block: 1057977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186471 RingCT/type: yes/0
Extra: 017f1cb5dacd2618d1338e9d53d4b1bc3bda96b5e0fc086b53f7315816784bdf260211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecf6346fa507fc4e9c6945088bbc96733e8b8484b4ca5cc41ba5a801d9ca669b 0.600000000000 1528420 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": 1057987, "vin": [ { "gen": { "height": 1057977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecf6346fa507fc4e9c6945088bbc96733e8b8484b4ca5cc41ba5a801d9ca669b" } } ], "extra": [ 1, 127, 28, 181, 218, 205, 38, 24, 209, 51, 142, 157, 83, 212, 177, 188, 59, 218, 150, 181, 224, 252, 8, 107, 83, 247, 49, 88, 22, 120, 75, 223, 38, 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