Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c65fa0485945b8df91d54ec48298d90a240198559ae216f06b748a503f368d42

Tx prefix hash: f525bcd367e6fd8fcda34cc5c5e0c39ab0d8ff1adc64a14ab12ce029ec6214cb
Tx public key: 7a01ca95ae19659855240a96a2f9f132572e3548284b08b88623429746070a5d
Timestamp: 1694171061 Timestamp [UCT]: 2023-09-08 11:04:21 Age [y:d:h:m:s]: 01:248:04:52:32
Block: 843606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438516 RingCT/type: yes/0
Extra: 017a01ca95ae19659855240a96a2f9f132572e3548284b08b88623429746070a5d02110000000e75e3f0e9000000000000000000

1 output(s) for total of 0.983519988000 dcy

stealth address amount amount idx
00: 6fa1b6abccb0de429d4edadb7cd4eac6f3e6da06dca28df6bd818d000a8538fb 0.983519988000 1296854 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": 843616, "vin": [ { "gen": { "height": 843606 } } ], "vout": [ { "amount": 983519988, "target": { "key": "6fa1b6abccb0de429d4edadb7cd4eac6f3e6da06dca28df6bd818d000a8538fb" } } ], "extra": [ 1, 122, 1, 202, 149, 174, 25, 101, 152, 85, 36, 10, 150, 162, 249, 241, 50, 87, 46, 53, 72, 40, 75, 8, 184, 134, 35, 66, 151, 70, 7, 10, 93, 2, 17, 0, 0, 0, 14, 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