Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4e2d5bec113214e4130088e251baa4a2a645e9a33e33cac2a9e40bb06e8a770

Tx prefix hash: a06690f343e9b96b685fa5f5ca4aab289a7ad7b8474f404099c846edc972f60d
Tx public key: 3cd3c89938e1f77663b526f2a116a1c76c33e5adcec5e6e2f277b7ff41ae30b1
Timestamp: 1729050694 Timestamp [UCT]: 2024-10-16 03:51:34 Age [y:d:h:m:s]: 00:246:09:16:30
Block: 1132605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175774 RingCT/type: yes/0
Extra: 013cd3c89938e1f77663b526f2a116a1c76c33e5adcec5e6e2f277b7ff41ae30b10211000000053cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9fb5736291248a09b7c542d41cc33b60f1ff2e5386726aae6082b5e4ebb0ac4 0.600000000000 1615560 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": 1132615, "vin": [ { "gen": { "height": 1132605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9fb5736291248a09b7c542d41cc33b60f1ff2e5386726aae6082b5e4ebb0ac4" } } ], "extra": [ 1, 60, 211, 200, 153, 56, 225, 247, 118, 99, 181, 38, 242, 161, 22, 161, 199, 108, 51, 229, 173, 206, 197, 230, 226, 242, 119, 183, 255, 65, 174, 48, 177, 2, 17, 0, 0, 0, 5, 60, 208, 252, 6, 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