Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 626e0d4bae3d2ec7ee4f659dbf842bfaae1fbd070a8b449570b6b2b6dd7a8b4a

Tx prefix hash: 1a52fd42fa397956f7534ebc502d272bee8443606da118ca1dbdbf005c32942e
Tx public key: 7f65727111075f3af8f0f8f0808c735caefeeefa91be534644640d9796b365aa
Timestamp: 1729949840 Timestamp [UCT]: 2024-10-26 13:37:20 Age [y:d:h:m:s]: 00:168:10:59:43
Block: 1140015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120185 RingCT/type: yes/0
Extra: 017f65727111075f3af8f0f8f0808c735caefeeefa91be534644640d9796b365aa0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b6c4c146dafbd4b3414b80b3a21d4e9cbed0e4ae74441b634396f92d3b4b8b2 0.600000000000 1623806 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": 1140025, "vin": [ { "gen": { "height": 1140015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b6c4c146dafbd4b3414b80b3a21d4e9cbed0e4ae74441b634396f92d3b4b8b2" } } ], "extra": [ 1, 127, 101, 114, 113, 17, 7, 95, 58, 248, 240, 248, 240, 128, 140, 115, 92, 174, 254, 238, 250, 145, 190, 83, 70, 68, 100, 13, 151, 150, 179, 101, 170, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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