Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75602c1123a4d6f7096e8575528d8115f8c6913af79f398f852f8a61c140f35a

Tx prefix hash: f6633a0b09eeebc174931f45896e90e16e36440f9333d0fafb931c1d96aa7700
Tx public key: fc4208d6fce120856e2ad39a83f949748403d6f524a35b49fb45d49743548aab
Timestamp: 1729926267 Timestamp [UCT]: 2024-10-26 07:04:27 Age [y:d:h:m:s]: 00:063:17:31:29
Block: 1139817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45546 RingCT/type: yes/0
Extra: 01fc4208d6fce120856e2ad39a83f949748403d6f524a35b49fb45d49743548aab021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36c0c0d2709ea8c07966f27f691a3a5283c2c0312897e6afb69964952cff4faf 0.600000000000 1623604 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": 1139827, "vin": [ { "gen": { "height": 1139817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36c0c0d2709ea8c07966f27f691a3a5283c2c0312897e6afb69964952cff4faf" } } ], "extra": [ 1, 252, 66, 8, 214, 252, 225, 32, 133, 110, 42, 211, 154, 131, 249, 73, 116, 132, 3, 214, 245, 36, 163, 91, 73, 251, 69, 212, 151, 67, 84, 138, 171, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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