Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f930ee2ee907ff99add6c4050fc9febd68d0fb9e7460514a3e376a889ac9dd94

Tx prefix hash: 806d46a7347578e6dbc98f533ed7ee72acd3838b68f58c67ffb4e33d821356a5
Tx public key: d21ea19155701ab37cb48eb927d45583e5df1a7c4bfa103e443530f14457d3d6
Timestamp: 1722343417 Timestamp [UCT]: 2024-07-30 12:43:37 Age [y:d:h:m:s]: 00:204:23:39:08
Block: 1076982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146367 RingCT/type: yes/0
Extra: 01d21ea19155701ab37cb48eb927d45583e5df1a7c4bfa103e443530f14457d3d6021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83dc30768be3dbdabfd53d0848df17222be3ff22170e9a7d5065d52876f8606d 0.600000000000 1549525 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": 1076992, "vin": [ { "gen": { "height": 1076982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83dc30768be3dbdabfd53d0848df17222be3ff22170e9a7d5065d52876f8606d" } } ], "extra": [ 1, 210, 30, 161, 145, 85, 112, 26, 179, 124, 180, 142, 185, 39, 212, 85, 131, 229, 223, 26, 124, 75, 250, 16, 62, 68, 53, 48, 241, 68, 87, 211, 214, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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