Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 641442fe477ead4313f072b00468286ad28144caef06b3eab6331394549b353e

Tx prefix hash: ae79b73f1d6dac66bea5f04bbd748b43429e3cad7564fa53fe5e7e8b209f5909
Tx public key: bc1b12ff557b5ae4cb5283e05de9aa41107ff2d4bbab9e8f6cfff1368294561f
Timestamp: 1716058034 Timestamp [UCT]: 2024-05-18 18:47:14 Age [y:d:h:m:s]: 00:307:16:12:41
Block: 1024875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219918 RingCT/type: yes/0
Extra: 01bc1b12ff557b5ae4cb5283e05de9aa41107ff2d4bbab9e8f6cfff1368294561f0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e9765f7ecaa4a2d8d03c04c026599f6e1f6030999abfa2841c2aff082c8b8de 0.600000000000 1490964 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": 1024885, "vin": [ { "gen": { "height": 1024875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e9765f7ecaa4a2d8d03c04c026599f6e1f6030999abfa2841c2aff082c8b8de" } } ], "extra": [ 1, 188, 27, 18, 255, 85, 123, 90, 228, 203, 82, 131, 224, 93, 233, 170, 65, 16, 127, 242, 212, 187, 171, 158, 143, 108, 255, 241, 54, 130, 148, 86, 31, 2, 17, 0, 0, 0, 5, 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