Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 018566bf02917ef1b03aeaa5299e783e1c10455bc30208e0f2906a8f09897581

Tx prefix hash: b6685f3d35907d850c937ab968f4271f5f5c808c439549b919534cd48c05caca
Tx public key: b211e9be3bd6fcbeb1bbc4fd36557ae41555decf5f8a2af2f3a224cb33326693
Timestamp: 1700952540 Timestamp [UCT]: 2023-11-25 22:49:00 Age [y:d:h:m:s]: 01:090:19:54:17
Block: 899637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326048 RingCT/type: yes/0
Extra: 01b211e9be3bd6fcbeb1bbc4fd36557ae41555decf5f8a2af2f3a224cb3332669302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.641400281000 dcy

stealth address amount amount idx
00: 74c7885f051b9db4ac4b987c6307352d1fff2d7b1323b73c7223e8cb6c0fe10a 0.641400281000 1356096 of 0

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": 899647, "vin": [ { "gen": { "height": 899637 } } ], "vout": [ { "amount": 641400281, "target": { "key": "74c7885f051b9db4ac4b987c6307352d1fff2d7b1323b73c7223e8cb6c0fe10a" } } ], "extra": [ 1, 178, 17, 233, 190, 59, 214, 252, 190, 177, 187, 196, 253, 54, 85, 122, 228, 21, 85, 222, 207, 95, 138, 42, 242, 243, 162, 36, 203, 51, 50, 102, 147, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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