Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6595f76ab78aad8bcafd47d307db36e2250dd6a3c51e0e5c13167f6d030a46b3

Tx prefix hash: 23fd323cebcd938df37a9e4d6ee289c1a1eeb7bcebc42103e909f13e5621f337
Tx public key: 2744b9a8a7fac2077682b606338f5a4aead70747375b38b84f30f5a5d8e51a22
Timestamp: 1725593358 Timestamp [UCT]: 2024-09-06 03:29:18 Age [y:d:h:m:s]: 00:225:04:29:44
Block: 1103926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160795 RingCT/type: yes/0
Extra: 012744b9a8a7fac2077682b606338f5a4aead70747375b38b84f30f5a5d8e51a2202110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e169f30ce14326eafd98c6ae30b78c7edf963954cd1a00ce86139d91f675d595 0.600000000000 1580945 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": 1103936, "vin": [ { "gen": { "height": 1103926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e169f30ce14326eafd98c6ae30b78c7edf963954cd1a00ce86139d91f675d595" } } ], "extra": [ 1, 39, 68, 185, 168, 167, 250, 194, 7, 118, 130, 182, 6, 51, 143, 90, 74, 234, 215, 7, 71, 55, 91, 56, 184, 79, 48, 245, 165, 216, 229, 26, 34, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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