Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 415effc5cbe38ececf75f8a12ed42a758fb729f2c0893bb629af5f93c126c0ba

Tx prefix hash: 628aa4050debfbc030f0c605be251f13b184d1108040792df17dd4bcf725be58
Tx public key: d8b358dd2d4f7533fab42add14fe3e59de4fb868c078eb15f3c9f79f2a5c2070
Timestamp: 1737503808 Timestamp [UCT]: 2025-01-21 23:56:48 Age [y:d:h:m:s]: 00:333:07:54:43
Block: 1202478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235829 RingCT/type: yes/0
Extra: 01d8b358dd2d4f7533fab42add14fe3e59de4fb868c078eb15f3c9f79f2a5c2070021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0adfbdb7074ca4b605c9cc609afe16fc07236f204416b8f312dc19690c45668 0.600000000000 1689143 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": 1202488, "vin": [ { "gen": { "height": 1202478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0adfbdb7074ca4b605c9cc609afe16fc07236f204416b8f312dc19690c45668" } } ], "extra": [ 1, 216, 179, 88, 221, 45, 79, 117, 51, 250, 180, 42, 221, 20, 254, 62, 89, 222, 79, 184, 104, 192, 120, 235, 21, 243, 201, 247, 159, 42, 92, 32, 112, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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