Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e8391fb50a0a85ffa507d96285a2f9434b709f3252c987ec9d6510590d99b1d

Tx prefix hash: f2023bc1e86e6e9b951fe67bef1ad06fbe0cc76c628ee355580e2fa665ad9195
Tx public key: 2cdc24af75d10ddf4c866a97f5c3c623f402efdc55c0511cf1b75b4c5063aafa
Timestamp: 1704350152 Timestamp [UCT]: 2024-01-04 06:35:52 Age [y:d:h:m:s]: 01:335:21:50:32
Block: 927814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498937 RingCT/type: yes/0
Extra: 012cdc24af75d10ddf4c866a97f5c3c623f402efdc55c0511cf1b75b4c5063aafa021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50c0e7ce76ad8542b54107aa67c4db14066bd0334e98102f55afc07c9fd9f2cc 0.600000000000 1385650 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": 927824, "vin": [ { "gen": { "height": 927814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50c0e7ce76ad8542b54107aa67c4db14066bd0334e98102f55afc07c9fd9f2cc" } } ], "extra": [ 1, 44, 220, 36, 175, 117, 209, 13, 223, 76, 134, 106, 151, 245, 195, 198, 35, 244, 2, 239, 220, 85, 192, 81, 28, 241, 183, 91, 76, 80, 99, 170, 250, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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