Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d4cd48af6efa9c52faa0d438f0e8b79aa8307996a074a734d3164079e8097aa

Tx prefix hash: 00b54e48545cefea9379baccb827766ee1714b2935471ac922d183874a5008dd
Tx public key: 7089f037a47025dc38dd1e2501fc53b5d5f9f0018bd716de1d0d7db3e229817d
Timestamp: 1713661685 Timestamp [UCT]: 2024-04-21 01:08:05 Age [y:d:h:m:s]: 00:278:22:11:13
Block: 1004997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199605 RingCT/type: yes/0
Extra: 017089f037a47025dc38dd1e2501fc53b5d5f9f0018bd716de1d0d7db3e229817d0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 958fae3d4c9aee5c91201f037566b29b4679024bcfc95b4cf596db7622b33eb8 0.600000000000 1465575 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": 1005007, "vin": [ { "gen": { "height": 1004997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "958fae3d4c9aee5c91201f037566b29b4679024bcfc95b4cf596db7622b33eb8" } } ], "extra": [ 1, 112, 137, 240, 55, 164, 112, 37, 220, 56, 221, 30, 37, 1, 252, 83, 181, 213, 249, 240, 1, 139, 215, 22, 222, 29, 13, 125, 179, 226, 41, 129, 125, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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