Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 105ae1443c0821a1471572c6812da36f041cc7aa657f3a5ec97324548dc51e16

Tx prefix hash: 3f7091d1177922b5611d672765c04690eec90495dbe4e7944aae6f9832e0b345
Tx public key: f5b23f333d3682456745c7f8a72f8b3b5519e804a7adfe610d0a8bbd593d497c
Timestamp: 1731030874 Timestamp [UCT]: 2024-11-08 01:54:34 Age [y:d:h:m:s]: 00:019:20:13:52
Block: 1148917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14204 RingCT/type: yes/0
Extra: 01f5b23f333d3682456745c7f8a72f8b3b5519e804a7adfe610d0a8bbd593d497c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f978e2be9216c3c195a5916fe05983cfc731d44e4b3aecf30a77f203d6143750 0.600000000000 1633884 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": 1148927, "vin": [ { "gen": { "height": 1148917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f978e2be9216c3c195a5916fe05983cfc731d44e4b3aecf30a77f203d6143750" } } ], "extra": [ 1, 245, 178, 63, 51, 61, 54, 130, 69, 103, 69, 199, 248, 167, 47, 139, 59, 85, 25, 232, 4, 167, 173, 254, 97, 13, 10, 139, 189, 89, 61, 73, 124, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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