Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379da5b7302872283559f6eb00301dc9ecc520edf574a38a28a6bfb6c10c614f

Tx prefix hash: b839a2972c5aa0df9bd3d8488d2c50653368e8ced2157d55b8856f4120b6693a
Tx public key: d92e24974966c213f1601c4fd515398ca0e877a95028b58dc64c3a1f4037fbcb
Timestamp: 1705264240 Timestamp [UCT]: 2024-01-14 20:30:40 Age [y:d:h:m:s]: 01:155:04:46:30
Block: 935369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371952 RingCT/type: yes/0
Extra: 01d92e24974966c213f1601c4fd515398ca0e877a95028b58dc64c3a1f4037fbcb0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 338293f3ccc310f47e650f38c3e27268488710c4b25650f5855276f27ec88fce 0.600000000000 1393385 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": 935379, "vin": [ { "gen": { "height": 935369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "338293f3ccc310f47e650f38c3e27268488710c4b25650f5855276f27ec88fce" } } ], "extra": [ 1, 217, 46, 36, 151, 73, 102, 194, 19, 241, 96, 28, 79, 213, 21, 57, 140, 160, 232, 119, 169, 80, 40, 181, 141, 198, 76, 58, 31, 64, 55, 251, 203, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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