Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80d712f11bf962cf78797dc2ba967fbaf8b172b42940f8f3c945631509391ae7

Tx prefix hash: 6b6be21bc4da6f0fc4049d928e69d5c2bec6704f9ab8399bceda0c6b0163f4f9
Tx public key: 65a76150335af8db7e4b9737b513e3377474e29c0bd65e445ca8ce4886944bca
Timestamp: 1729950299 Timestamp [UCT]: 2024-10-26 13:44:59 Age [y:d:h:m:s]: 00:028:21:17:30
Block: 1140019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20623 RingCT/type: yes/0
Extra: 0165a76150335af8db7e4b9737b513e3377474e29c0bd65e445ca8ce4886944bca021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d91606555efb22eb6a8a10ab1abc3daff4bf2561dd054d636ce4f453d4fbd23 0.600000000000 1623810 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": 1140029, "vin": [ { "gen": { "height": 1140019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d91606555efb22eb6a8a10ab1abc3daff4bf2561dd054d636ce4f453d4fbd23" } } ], "extra": [ 1, 101, 167, 97, 80, 51, 90, 248, 219, 126, 75, 151, 55, 181, 19, 227, 55, 116, 116, 226, 156, 11, 214, 94, 68, 92, 168, 206, 72, 134, 148, 75, 202, 2, 17, 0, 0, 0, 4, 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