Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 173e65cd8846fa1c90e81ba0698c58581022d611e7d0d5ce065b5ff50041df0e

Tx prefix hash: 7d61339226ac3ce054effb5061da26d3eb91527fb2576fee2b85a081fadf5378
Tx public key: 09374cbe444a4a8de84509ec9436cdab8e8e4d7b223e2ef82fffa9e3062c13db
Timestamp: 1707125801 Timestamp [UCT]: 2024-02-05 09:36:41 Age [y:d:h:m:s]: 01:291:05:39:51
Block: 950812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466935 RingCT/type: yes/0
Extra: 0109374cbe444a4a8de84509ec9436cdab8e8e4d7b223e2ef82fffa9e3062c13db02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6becaed22c07104e06ac875e3058b90a0090cd832fb14300e66452414db6f65 0.600000000000 1409490 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": 950822, "vin": [ { "gen": { "height": 950812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6becaed22c07104e06ac875e3058b90a0090cd832fb14300e66452414db6f65" } } ], "extra": [ 1, 9, 55, 76, 190, 68, 74, 74, 141, 232, 69, 9, 236, 148, 54, 205, 171, 142, 142, 77, 123, 34, 62, 46, 248, 47, 255, 169, 227, 6, 44, 19, 219, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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