Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd3e5dcc5b924b075101e62731a3f0c51e740ca7251f72f8f23014b5a3b56497

Tx prefix hash: cf90d5ec3541611b8d96479e0005f68765beb4368f0f93e7cc317bc6c23c35a4
Tx public key: 20ec1c46d38f1f7dcc9ff6b6aaaeaf9cf3b641d257a3d5fe379fca78a8844fb3
Timestamp: 1698494095 Timestamp [UCT]: 2023-10-28 11:54:55 Age [y:d:h:m:s]: 02:039:13:05:07
Block: 879492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547853 RingCT/type: yes/0
Extra: 0120ec1c46d38f1f7dcc9ff6b6aaaeaf9cf3b641d257a3d5fe379fca78a8844fb30211000000094b8f5122000000000000000000

1 output(s) for total of 0.747959225000 dcy

stealth address amount amount idx
00: 22f236b750d0fe36791e5a76e3952407ece6d3feb783b771921bd429c092ce96 0.747959225000 1335018 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": 879502, "vin": [ { "gen": { "height": 879492 } } ], "vout": [ { "amount": 747959225, "target": { "key": "22f236b750d0fe36791e5a76e3952407ece6d3feb783b771921bd429c092ce96" } } ], "extra": [ 1, 32, 236, 28, 70, 211, 143, 31, 125, 204, 159, 246, 182, 170, 174, 175, 156, 243, 182, 65, 210, 87, 163, 213, 254, 55, 159, 202, 120, 168, 132, 79, 179, 2, 17, 0, 0, 0, 9, 75, 143, 81, 34, 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