Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ee113b69a694ee46fe89ab221cdb546aca447ea8d512c27d50659423f696268

Tx prefix hash: 02cda1bca6a58c1ab00acb01e4d5a459926a4b65d3bb1317372548b894755f71
Tx public key: 94d43c6298fd5c07f81164837b156f3d724b88bf3f0c123bf4a39df907a891e4
Timestamp: 1703478909 Timestamp [UCT]: 2023-12-25 04:35:09 Age [y:d:h:m:s]: 01:123:19:19:00
Block: 920596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349604 RingCT/type: yes/0
Extra: 0194d43c6298fd5c07f81164837b156f3d724b88bf3f0c123bf4a39df907a891e402110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a76b6327ca0f18e9ee9c554bd073296d4176415cca3a0e047f51dae395001d6a 0.600000000000 1378276 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": 920606, "vin": [ { "gen": { "height": 920596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a76b6327ca0f18e9ee9c554bd073296d4176415cca3a0e047f51dae395001d6a" } } ], "extra": [ 1, 148, 212, 60, 98, 152, 253, 92, 7, 248, 17, 100, 131, 123, 21, 111, 61, 114, 75, 136, 191, 63, 12, 18, 59, 244, 163, 157, 249, 7, 168, 145, 228, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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