Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f163504dfc693bb14e9eac4320f07616967c0686600612c3082da5dc059329d6

Tx prefix hash: 38313c7c12e46b8d86935017637a8d05cf0ffc5b0afe999ffb2062c46ea18b70
Tx public key: a68c81d7b3a416e9c4c12562da4a7ef0614a3ab51a2914af13ff1d6651a9d15c
Timestamp: 1725282934 Timestamp [UCT]: 2024-09-02 13:15:34 Age [y:d:h:m:s]: 00:083:00:30:49
Block: 1101348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59378 RingCT/type: yes/0
Extra: 01a68c81d7b3a416e9c4c12562da4a7ef0614a3ab51a2914af13ff1d6651a9d15c02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d19a006eaa854225972dc4663eea67907b2f6455efe85a2102125afb32cded1 0.600000000000 1577365 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": 1101358, "vin": [ { "gen": { "height": 1101348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d19a006eaa854225972dc4663eea67907b2f6455efe85a2102125afb32cded1" } } ], "extra": [ 1, 166, 140, 129, 215, 179, 164, 22, 233, 196, 193, 37, 98, 218, 74, 126, 240, 97, 74, 58, 181, 26, 41, 20, 175, 19, 255, 29, 102, 81, 169, 209, 92, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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