Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3023365a5d8e18a2b5e4f6981f97947f6147861ad9e28e17fd6d32f6b03b43d9

Tx prefix hash: e628d4dbad11d89e68e5a3e7d094418e59b2b7a424852d6da23cec85d5a691c2
Tx public key: a0721da260364ca53dd200e95e4b59c562ee17bcf9124c17ca9a30022133d323
Timestamp: 1721513693 Timestamp [UCT]: 2024-07-20 22:14:53 Age [y:d:h:m:s]: 00:261:23:05:37
Block: 1070102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187138 RingCT/type: yes/0
Extra: 01a0721da260364ca53dd200e95e4b59c562ee17bcf9124c17ca9a30022133d32302110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7da0dabd446f37b6f038afd50a007037450d77ccb23d0f343b65eb94e3dd691 0.600000000000 1541797 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": 1070112, "vin": [ { "gen": { "height": 1070102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7da0dabd446f37b6f038afd50a007037450d77ccb23d0f343b65eb94e3dd691" } } ], "extra": [ 1, 160, 114, 29, 162, 96, 54, 76, 165, 61, 210, 0, 233, 94, 75, 89, 197, 98, 238, 23, 188, 249, 18, 76, 23, 202, 154, 48, 2, 33, 51, 211, 35, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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