Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41d6113b2045667693304add2c1a20cf0f650317744236944c1a891e135f48ae

Tx prefix hash: e58e54ea0c1d5d9ba4c95fc13ca8cc0a4dd7c66aff967afea64c3d3f79430e10
Tx public key: bcee8be8b29a52b00fb323ecc389b81fcc1e13cb437cdc702d64c25815797c07
Timestamp: 1711820766 Timestamp [UCT]: 2024-03-30 17:46:06 Age [y:d:h:m:s]: 00:354:05:41:04
Block: 989763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253274 RingCT/type: yes/0
Extra: 01bcee8be8b29a52b00fb323ecc389b81fcc1e13cb437cdc702d64c25815797c070211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d9ae5dc3a33c9b50e30d0c5331883d0a7e86ef3aacdf7fa0265e6e0f7cfff97 0.600000000000 1450081 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": 989773, "vin": [ { "gen": { "height": 989763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d9ae5dc3a33c9b50e30d0c5331883d0a7e86ef3aacdf7fa0265e6e0f7cfff97" } } ], "extra": [ 1, 188, 238, 139, 232, 178, 154, 82, 176, 15, 179, 35, 236, 195, 137, 184, 31, 204, 30, 19, 203, 67, 124, 220, 112, 45, 100, 194, 88, 21, 121, 124, 7, 2, 17, 0, 0, 0, 1, 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