Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5178d993351babc1c3e87245032a8a7402cd0ae2be90c0d7542240c98333fee9

Tx prefix hash: dcc3594467102890aba0fd732db984516926829795fe92fc4efd8611e85cf3a4
Tx public key: dd64d57be5f187f2920e18d7aad0f6c4ce244d15a34192af990d3c4b894b266f
Timestamp: 1724421000 Timestamp [UCT]: 2024-08-23 13:50:00 Age [y:d:h:m:s]: 00:266:15:23:54
Block: 1094223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190441 RingCT/type: yes/0
Extra: 01dd64d57be5f187f2920e18d7aad0f6c4ce244d15a34192af990d3c4b894b266f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 080c81ecc20d518fc82b4740f3c87f9318ea4108f0f69ab58263a56e2ea75f3d 0.600000000000 1569326 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": 1094233, "vin": [ { "gen": { "height": 1094223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "080c81ecc20d518fc82b4740f3c87f9318ea4108f0f69ab58263a56e2ea75f3d" } } ], "extra": [ 1, 221, 100, 213, 123, 229, 241, 135, 242, 146, 14, 24, 215, 170, 208, 246, 196, 206, 36, 77, 21, 163, 65, 146, 175, 153, 13, 60, 75, 137, 75, 38, 111, 2, 17, 0, 0, 0, 2, 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