Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce3d370005b6426fa5e1419322bcb87c7b9f043c8543b1e7fc3594d46d4c777f

Tx prefix hash: b33fc9386865b50f6305ffd0171b48033cf4fec9dadcf0080cc0ceae8f6126b3
Tx public key: ee3ff1e527d4b88a6ddf7129c61bc96e6a3beb45540afb4ebcbe0cf75ea73f50
Timestamp: 1709407701 Timestamp [UCT]: 2024-03-02 19:28:21 Age [y:d:h:m:s]: 01:036:00:22:05
Block: 969748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286730 RingCT/type: yes/0
Extra: 01ee3ff1e527d4b88a6ddf7129c61bc96e6a3beb45540afb4ebcbe0cf75ea73f500211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9e3833c70f96930c59b08402e980d19f9008f0a7bcf34c244193d5de441d25c 0.600000000000 1429589 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": 969758, "vin": [ { "gen": { "height": 969748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9e3833c70f96930c59b08402e980d19f9008f0a7bcf34c244193d5de441d25c" } } ], "extra": [ 1, 238, 63, 241, 229, 39, 212, 184, 138, 109, 223, 113, 41, 198, 27, 201, 110, 106, 59, 235, 69, 84, 10, 251, 78, 188, 190, 12, 247, 94, 167, 63, 80, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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