Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68d89409eb7c6c2a8ad0a5269746fcf09cc71f185ae779f43917ed112411ccf

Tx prefix hash: 3bc55a4a8616507d7aad9d69b37fbbb9db6fdaf323a7c91d90db41d69dd63fdd
Tx public key: be8a29db50a11843c14e83ec7eae0c856fc87e093aa00675837ad4e9fbaddee0
Timestamp: 1710230700 Timestamp [UCT]: 2024-03-12 08:05:00 Age [y:d:h:m:s]: 00:246:03:43:12
Block: 976583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176210 RingCT/type: yes/0
Extra: 01be8a29db50a11843c14e83ec7eae0c856fc87e093aa00675837ad4e9fbaddee00211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f196f9f9162033d13990532b95b1c9a2d58ec48d2c30c3070638e1c09715e95 0.600000000000 1436578 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": 976593, "vin": [ { "gen": { "height": 976583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f196f9f9162033d13990532b95b1c9a2d58ec48d2c30c3070638e1c09715e95" } } ], "extra": [ 1, 190, 138, 41, 219, 80, 161, 24, 67, 193, 78, 131, 236, 126, 174, 12, 133, 111, 200, 126, 9, 58, 160, 6, 117, 131, 122, 212, 233, 251, 173, 222, 224, 2, 17, 0, 0, 0, 5, 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