Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8a53923628b62cda9c1d97e30b214863085f75e149c206c6aae1eee1113f564

Tx prefix hash: ffa276bc439d6c74bd833876b6d2469e6bb96d43155829aade4ee235df2cc58f
Tx public key: a84f36f0fbbc0267ec38de027aa5b148b465975401bc6f541db14acf3c053a94
Timestamp: 1711214681 Timestamp [UCT]: 2024-03-23 17:24:41 Age [y:d:h:m:s]: 01:085:12:32:46
Block: 984747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322008 RingCT/type: yes/0
Extra: 01a84f36f0fbbc0267ec38de027aa5b148b465975401bc6f541db14acf3c053a9402110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6b29fb612e528ede198eb2b646cb5a58c7c879f8554fdac1bd5df40297d1e08 0.600000000000 1444920 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": 984757, "vin": [ { "gen": { "height": 984747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6b29fb612e528ede198eb2b646cb5a58c7c879f8554fdac1bd5df40297d1e08" } } ], "extra": [ 1, 168, 79, 54, 240, 251, 188, 2, 103, 236, 56, 222, 2, 122, 165, 177, 72, 180, 101, 151, 84, 1, 188, 111, 84, 29, 177, 74, 207, 60, 5, 58, 148, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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