Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cf643d8143180afe9ba1e6186095a48882b93e6418e7ceec349cfaed1a83108

Tx prefix hash: dcdb1f1bf4bda39dcdc404cd4b270b48e09ec44bb35af0f51a1c30f4bf53a8e4
Tx public key: 640f41ecb4967e4263b525ddb9afe7d154dc2a73ba7258e6fbbb362c73efa60d
Timestamp: 1721684607 Timestamp [UCT]: 2024-07-22 21:43:27 Age [y:d:h:m:s]: 00:268:11:32:25
Block: 1071504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191822 RingCT/type: yes/0
Extra: 01640f41ecb4967e4263b525ddb9afe7d154dc2a73ba7258e6fbbb362c73efa60d021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1861dc483be3087ca3bbbf204ae7f6849e7b94fb8ed284316f84a3f57b00ab0 0.600000000000 1543763 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": 1071514, "vin": [ { "gen": { "height": 1071504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1861dc483be3087ca3bbbf204ae7f6849e7b94fb8ed284316f84a3f57b00ab0" } } ], "extra": [ 1, 100, 15, 65, 236, 180, 150, 126, 66, 99, 181, 37, 221, 185, 175, 231, 209, 84, 220, 42, 115, 186, 114, 88, 230, 251, 187, 54, 44, 115, 239, 166, 13, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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