Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59004cf409f4b33af38d646463b6f446e0bff2fc76dabffbf4d9dc3ae10fb146

Tx prefix hash: 2c258a27975bb24083536d87f461df89f0707b4a8018af23adbc2c37330e9098
Tx public key: 0a0f953846427ceca1d40729e970e9848269c55f5b93d51bfe9218ea07a2f5e7
Timestamp: 1672888304 Timestamp [UCT]: 2023-01-05 03:11:44 Age [y:d:h:m:s]: 02:096:01:16:05
Block: 667834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590342 RingCT/type: yes/0
Extra: 010a0f953846427ceca1d40729e970e9848269c55f5b93d51bfe9218ea07a2f5e702110000000352542ceb000000000000000000

1 output(s) for total of 3.760007293000 dcy

stealth address amount amount idx
00: b486090b3d2314ead3c0f2fcaec66b4741e61a26b839afff861303df036fd27d 3.760007293000 1109053 of 0

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": 667844, "vin": [ { "gen": { "height": 667834 } } ], "vout": [ { "amount": 3760007293, "target": { "key": "b486090b3d2314ead3c0f2fcaec66b4741e61a26b839afff861303df036fd27d" } } ], "extra": [ 1, 10, 15, 149, 56, 70, 66, 124, 236, 161, 212, 7, 41, 233, 112, 233, 132, 130, 105, 197, 95, 91, 147, 213, 27, 254, 146, 24, 234, 7, 162, 245, 231, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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