Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e1911ae4393195ba1484b9834870dd5af0ef756d9693f51de2c37f84c5df5c3

Tx prefix hash: 8222a0bee39f1eaefa560165024bd47074ab6170d225ddbdd93c6279b1a06279
Tx public key: d7ec81d34f9607b9a171a9c5c7fa9e4d88ac14d2cccd3261f645a1b6c94de5c4
Timestamp: 1737619896 Timestamp [UCT]: 2025-01-23 08:11:36 Age [y:d:h:m:s]: 00:146:21:56:01
Block: 1203436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104715 RingCT/type: yes/0
Extra: 01d7ec81d34f9607b9a171a9c5c7fa9e4d88ac14d2cccd3261f645a1b6c94de5c4021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 341697d783735c60a7a11e4a979d76afbf27d8eec0dd0646946d826207184325 0.600000000000 1690113 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": 1203446, "vin": [ { "gen": { "height": 1203436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "341697d783735c60a7a11e4a979d76afbf27d8eec0dd0646946d826207184325" } } ], "extra": [ 1, 215, 236, 129, 211, 79, 150, 7, 185, 161, 113, 169, 197, 199, 250, 158, 77, 136, 172, 20, 210, 204, 205, 50, 97, 246, 69, 161, 182, 201, 77, 229, 196, 2, 17, 0, 0, 0, 9, 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